User interface for multi-media communication for the disabled

ABSTRACT

A method, user interface module, computer program product, computer system and system that enable a graphical user interface to be used by persons with visual disabilities. The graphical user interface includes a toolbar, which provides features that enable a visually disabled user to navigate and activate the functions provided by buttons or other controls on the communication toolbar. As a user navigates around the user interface, auditory messages are read describing functionality of different features of the graphical user interface. The text can be audibly read by, for example, a screen reader module. By using a hotkey or menu navigation, a user can issue commands that would normally be issued by clicking on the toolbar. Furthermore, the user can type text into text input boxes, select items from combo boxes, enable broadcast messages to be read, and choose to listen to status messages.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to application Ser. No. 09/823,531 (attorney docket M-11528 US, client reference SIEB062/US), filed on Mar. 31, 2001, entitled “User Interface for Multi-Channel Communication” and naming Mingte Chen, Anil K. Annadata, and Kuang Huang as inventors, the application being incorporated herein by reference in its entirety.

Portions of this patent application contain materials that are subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document, or the patent disclosure, as it appears in the Patent and Trademark Office file or records, but otherwise reserves all copyright rights whatsoever.

BACKGROUND OF THE INVENTION

Section 508 of the amended Rehabilitation Act of 1998 extends to web-based software applications the same legal guarantees of access that all physical public amenities must provide. The law now requires that new government web sites, and some existing web sites, make their content and functionality available to people with motor, visual or auditory disabilities.

Persons with auditory disabilities are typically able to use web sites. The toolbars and menus used to navigate web sites are navigable using a pointing device, sometimes referred to as a mouse, without the need for the user to hear auditory signals. Furthermore, special devices are available for those with motor disabilities that can be used to perform the functionality of a pointing device. However, enabling a user interface to be usable by the visually disabled presents special challenges, as pointing devices need visual interaction to operate.

One solution to enable a visually disabled person to use a web site is to use screen reader software to read the text of the web page. Screen reader software can detect textual messages presented by a user interface and read those messages to the user in a configurable voice. The visually disabled person can then hear audible text describing the web page and use a special device, such as a Braille keyboard, to enter the information needed to navigate the user interface.

However, most information used to navigate a web site does not appear as text on the web page. With the predominance of graphical user interfaces and the increasing sophistication of web-based user interfaces, text-based user interfaces are being replaced by user interfaces including icons, buttons, and other sophisticated sets of image-based controls such as toolbars. Screen readers cannot read, for example, tool tips or icon data.

What is needed is a graphical user interface that can be navigated by a person with visual disabilities.

SUMMARY OF THE INVENTION

The present invention relates to a method, system, user interface module, computer system, and computer program product that enable a graphical user interface to be used by persons with visual disabilities. The graphical user interface includes a toolbar, which provides features that enable a visually disabled user to navigate and activate the functions provided by buttons or other controls on the communication toolbar. As a user navigates around the user interface, auditory messages are read describing functionality of different features of the graphical user interface. The text can be audibly read by, for example, a screen reader module. By using a hotkey or menu navigation, a user can issue commands that would normally be issued by clicking on the toolbar. Furthermore, the user can type text into text input boxes, select items from combo boxes, enable broadcast messages to be read, and choose to listen to status messages.

In one feature, a method includes determining that a readable control of a user interface is activated and identifying a command associated with activation of the readable control. The identifying the command can include using a mapping between the readable control and a functional control. The method can further include issuing the command. In addition, the method can further include providing text for an audible message associated with the readable control. In one embodiment, the method further includes determining that a second readable control has obtained focus and providing text for an audible message associated with the second readable control.

In another feature, a method includes causing a state of a readable control of a user interface to change in response to obtaining an event. The method can further include providing text for an audible message in response to the change in the state.

In another feature of the invention, a interface module includes determining instructions to determine that a readable control of a user interface presented by the user interface module module is activated and identifying instructions to identify a command associated with activation of the readable control.

In yet another feature, a user interface module includes causing instructions to cause a state of a readable control of a user interface presented by the user interface module to change in response to obtaining an event.

In another feature of the invention, a system includes determining means for determining that a readable control of a user interface is activated and identifying means for identifying a command associated with activation of the readable control.

In still another feature of the invention, a system includes causing means for causing a state of a readable control of a user interface to change in response to obtaining an event In another feature of the invention, a computer program product includes determining instructions to determine that a readable control of a user interface is activated, identifying instructions to identify a command associated with activation of the readable control, and a computer-readable medium to store the determining instructions and the identifying instructions.

In still another feature of the invention, a computer program product includes causing instructions to cause a state of a readable control of a user interface to change in response to obtaining an event and a computer-readable medium to store the causing instructions.

In another feature of the invention, a computer system includes a processor for executing computer instructions and a memory comprising the computer instructions. The computer instructions include determining instructions to determine that a readable control of a user interface is activated, and identifying instructions to identify a command associated with activation of the readable control.

In another feature of the invention, a computer system includes a processor for executing computer instructions and a memory comprising the computer instructions. The computer instructions include causing instructions to cause a state of a readable control of a user interface to change in response to obtaining an event.

The foregoing is a summary and thus contains, by necessity, simplifications, generalizations and omissions of detail; consequently, those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the present invention, as defined solely by the claims, will become apparent in the non-limiting detailed description set forth below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention may be better understood, and its numerous objects, features and advantages made apparent to those skilled in the art by referencing the accompanying drawings.

FIG. 1 provides an example of a user interface that operates according to the present invention.

FIG. 2 shows the toolbar of the user interface of FIG. 1, including the individual controls on the toolbar.

FIG. 3 shows an example of the operation of the user interface of FIG. 2 in issuing a command, such as making an outgoing telephone call.

FIG. 4 shows another example of the operation of the user interface of FIG. 2 in receiving an event, such as receiving an incoming customer telephone call.

FIG. 5 is a block diagram illustrating a computer system suitable for implementing embodiments of the present invention.

The use of the same reference symbols in different drawings indicates similar or identical items. While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the Drawings and are described herein in detail. It should be understood, however, that the Drawings and Detailed Description are not intended to limit the invention to the particular form disclosed. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the scope of the present invention as defined by the appended Claims.

DETAILED DESCRIPTION

For a thorough understanding of the subject invention, refer to the following Detailed Description, including the appended Claims, in connection with the above-described Drawings. Although the present invention is described in connection with several embodiments, the invention is not intended to be limited to the specific forms set forth herein. On the contrary, it is intended to cover such alternatives, modifications, and equivalents as can be reasonably included within the scope of the invention as defined by the appended Claims.

In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the invention. It will be apparent, however, to one skilled in the art that the invention can be practiced without these specific details.

References in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Moreover, various features are described which may be exhibited by some embodiments and not by others. Similarly, various requirements are described which may be requirements for some embodiments but not other embodiments.

Introduction

The present invention provides a method, system, user interface module, computer system, and computer program product that enable a graphical user interface to be used by persons with visual disabilities. The graphical user interface includes a toolbar, which provides features that enable a visually disabled user to navigate and activate the functions provided by buttons or other controls on the communication toolbar. As a user navigates around the user interface, auditory messages are read describing functionality of different features of the graphical user interface. The text can be audibly read by, for example, a screen reader module. By using a hotkey or menu navigation, a user can issue commands that would normally be issued by clicking on the toolbar. Furthermore, the user can type text into text input boxes, select items from combo boxes, enable broadcast messages to be read, and choose to listen to status messages.

FIG. 1 provides an example of a user interface that operates according to the present invention. User interface 100 is presented by a web browser client 104 and provides a multi-media communication user interface for a customer service agent, also referred to herein as a user. Using only a web browser to access the multi-media communication user interface, a user can communicate with customers via several types of media, including telephone, e-mail, facsimile, wireless messages, and pager messages One of ordinary skill in the art will recognize that the present invention is not limited to a customer service or communication application, or to a particular web-browser based user interface, but rather is extensible to any user interface.

In one embodiment, the user interface of FIG. 1 has the same appearance and functionality for all users, both those visually disabled and those with vision. However, different toolbars are visible and active, depending upon whether the user has vision. In one embodiment, a Java toolbar, also referred to herein as a functional toolbar, is presented for users with vision and has functions that are invoked when a Java toolbar button is activated. For visually disabled users, an HTML toolbar, also referred to as a readable toolbar, is presented.

HTML controls can, for example, provide text that can be read by a screen reader (not shown). However, the HTML language does not provide the robust functionality that full-featured controls supported by programming languages can, such as Java or Active X controls.

Referring to FIG. 1, web browser client 104 provides standard browser controls 102 and application menu 101. Readable toolbar 103 provides access to multi-media communication channels. For example, Initiate Work Item button 107 and Initiate Phone Call button 108 are examples of controls providing access to multi-media communication. Further explanation of the controls of readable toolbar 103 is provided with reference to FIG. 2.

Readable toolbar 103 can be, for example, a set of HTML controls. In user interface 100, a mapping is provided from each control of readable toolbar 103 to a corresponding control on a functional toolbar 105 (not shown) that is active for users with vision. This mapping to functional toolbar 105 enables user interface 100 to provide equivalent functionality when an HTML control is activated. The relationship between readable toolbar 103 and functional toolbar 105 is described in further detail with reference to FIGS. 3 and 4 below.

Application data frame 150 includes data provided by the customer service application. The user currently is accessing customer contact information. Customer Dashboard frame 160 provides additional information about the customer for which contact data is displayed in Application Data frame 150. Message Broadcast frame 140 enables all users of the customer service application to receive broadcast messages.

In the example provided in FIG. 1, the agent is currently participating in a telephone call with a caller having telephone number 1-650-477-5000, as indicated in the Active Work Item combo box 180. Status Indicator 190 indicates that the call is currently connected. The agent has currently placed focus on Release button 170, and dynamic tooltip 172 indicates that activating the button currently in focus, for example, by pressing the enter key, will release the currently active call. For a visually disabled user, the “Release Call” text of the dynamic tooltip is read by screen reader software to provide an audible message to the user.

The user interface of FIG. 1 is configured such that a visually disabled user can use a keyboard to navigate, rather than a pointing device, such as a mouse. For example, depressing the tab key moves the user from one frame to the next. For frames including a set of controls, such as a toolbar, the tab key moves the cursor from one control to the next. Depressing the tab key places the next control “in focus.” When the focus changes from one control to another, a screen reader can read text associated with the control. For example, an audible message indicating the name of the control, such as “Release call,” may be read when the user places Release button 170 in focus.

An audible message for a control also may include status information about the control in focus. For example, a control may be in one of several states, such as an enabled state, a disabled state, a blinking state, and a toggled state. An example of an enabled state is the Release button 170 when the user is currently connected on a telephone call. When the user is not connected on a telephone call or other active work item, Release button 170 is disabled. An example of a blinking state is when a button on the toolbar blinks to capture the user's attention. For a visually disabled user, an audible sound is played to capture the user's attention. An example of a toggled button is a login button. The login button is toggled “on” when a user is logged in, and the login button is toggled “off” when the user logs out.

When the enter key is pressed on a control in focus, the effect is similar to that of a mouse click, and a function associated with the control is activated. For example, pressing the enter key while focused on the Release button 170 releases the telephone call currently connected to extension 27416. The effect is the same as if the agent had hung up a telephone handset.

The user interface of the present invention also provides configurable hot keys. For example, rather than using a tab key to tab from one control to the next, a hot key can be defined as a shortcut to perform a particular function. For example, a ctrl-R key sequence may be defined to release a telephone call, rather than requiring the user to tab to the Release button 170 and press the enter key.

Similarly, the user interface of the present invention is configurable to read messages associated with dynamic tooltips, messages in the message broadcast frame 140, status information from status indicator 190, and so on. As an example, consider the example where the user has placed Release button 170 in focus. The user can trigger a hot key, such as the H key, to obtain help, which will audibly read dynamic tooltip 172.

FIG. 2 shows the toolbar of the user interface of FIG. 1, including the individual controls on the toolbar. Because readable toolbar 103 provides a single user interface for the agent to communicate using multiple communication channels of different media types, this embodiment of readable toolbar 103 includes a media indicator button 202 to show the media type of the currently active work item. Customer waiting time button 204 shows the amount of time that the customer has been waiting to receive a response to his or her customer support request associated with the work item. This information allows the agent to be responsive to the customer, for example, by apologizing when the customer has been waiting for a long time on hold on the telephone. Working time window 206 shows the amount of time the agent has spent working on the currently active work item. Edit box 208 allows the user to enter a small command, such as an extension number for dialing the telephone or a short message to be sent via short messaging service.

Work item buttons 280 include buttons for enabling the agent to manage all of his or her active work items for all media types and communication channels. Initiate work item button 210 enables the agent to initiate a work item of the current media type, as indicated by media indicator button 202. As shown in the example, the user may choose to use the telephone, email, fax, wireless messaging, or paging. The media types shown are determined by a communication server (not shown) by accessing a customer support center database (not shown) to obtain the customer support center configuration to which the agent belongs. The communication server then uses the customer support center configuration to eliminate the media types of the communication channels for which the agent cannot access.

The icon shown on Initiate Work Item button 210 includes symbols representing multiple media types of telephone, email, and paging. The icon is used to show that the initiate work item is an abstract icon representing a work item for any media type. If the agent clicks on the initiate button 210 when displaying the abstract icon, readable toolbar 103 will determine from the context of the toolbar what the agent is trying to do. For instance, if the user is currently on the telephone with a customer, media indicator button 202 will show a telephone. If the agent simultaneously is viewing an email address for a contact and the user clicks on the initiate work item button, readable toolbar 103 will determine that, because the agent is already on the telephone and the contact has an email address, the agent must be trying to send an email to the contact. Readable toolbar 103 can be configured so that the new email screen is loaded with the customer information in order to save the agent time in typing the email. Readable toolbar 103 is configurable by an administrator using a configuration user interface.

Initiate Phone Call button 211 enables the user to initiate a telephone call and will prompt the user for the telephone number or dial the telephone number entered by the user in edit box 208. Initiate e-mail button 212 enables the user to write an e-mail, initiate fax button 213 enables the user to prepare a fax message, and initiate wireless message button 214 enables the user to send a message to a wireless device, such as a cellular telephone. Initiate page button enables the user to send a message to a pager.

Accept work item button 216 allows the user to accept an incoming work item. Notification of an incoming work item is provided by readable toolbar 103 using a notification function. For example, the notification function can cause an audible sound or voice message to be provided when the agent has an incoming work item. When the agent accepts a work item, a command is sent by web browser client 104 to a communication server, which responds to the command by issuing the command to a communication channel.

Accept work item button 216 enables the agent to select from a list of incoming work items. Accept phone button 217 enables the agent to accept an incoming telephone call, accept e-mail button 218 enables the agent to accept an incoming e-mail, and accept web collaboration button 219 enables the agent to accept a request for a web collaboration with a customer.

Release button 209 is used to release an active work item. In one embodiment, a communication server can be configured to release the telephone call work item automatically when the agent hangs up the telephone handset without clicking the release button 209. The hardware controlling the telephone connection sends a disconnect signal to the telephone switch to disconnect the agent's and customer's telephone lines.

Transfer buttons 284 are related to transferring work items such as telephone calls. Blind transfer button 220 enables the agent to transfer a telephone call to another extension and hang up without confirming whether an agent at the extension accepted the telephone call. If the telephone call is not accepted by another agent, the customer service application can be configured to place the telephone call as a work item into a queue of work items for transferring to another agent. The telephone call is removed from the transferring agent's list of active work items.

Consultative transfer button 222 enables an agent to consult with an agent at another extension before the call is transferred and to keep the telephone call if the other agent does not answer. Conference button 224 enables the agent to connect more than two telephone lines together for a joint telephone conversation. Retrieve button 226 enables the agent to retrieve a telephone call that the agent has transferred.

Suspend button 230 enables an agent to suspend a work item; for example, the agent can put a telephone call on hold or suspend writing an email response to work on another work item or take a break. Active work items window 232 enables the agent to see the currently active work item. Select work item control 294 enables the agent to select a work item from the list of work items currently assigned to the agent. Resume button 234 allows the agent to resume work on a work item selected from the list of work items.

Forward button 240 applies to media types such as telephones and email. All telephone calls to a particular telephone number can be automatically forwarded to another telephone number when, for example, an agent is away from his usual work location. In the context of media types such as email, forward button command 240 can be configured to operate as a forward command, retaining a copy of the original email or as “transfer” of the email removing the email from the agent's inbox and from the agent's list of active work items.

Because the customer service application is designed to monitor and provide real time information to agents, the agent needs a means of communicating his or her availability to accept work items from the customer service application. Change ready state button enables the user to update his status from “ready” to receive incoming work items to “not ready.” Change Ready State button 260 is an example of a button that can be toggled from one state to another. Buttons 262, 264, and 266 enable the user to change state for a single medium. For example, Change Ready State of Answer Phone button 262 allows a user to indicate that he is not ready to accept telephone calls; Change Ready State of Answer E-mail button 264 allows a user to indicate that he is not ready to receive e-mail work items; and Change Ready State of Answer Web Collaboration button 266 enables a user to indicate that he is not ready to answer a request for a web collaboration.

Login button 250 allows the agent to login to the customer service application to work on work items. Logout button 252 allows the agent to logout from the customer service application.

Because the operation of each button of readable toolbar 103 is configurable by associating a control with a command, readable toolbar 103 provides maximum flexibility in providing its customer support center with a tool for communicating via multiple communication channels of different media types.

FIG. 3 shows an example of the operation of the toolbar of FIG. 2 in issuing a command, such as making an outgoing telephone call. In action 3.1, the agent navigates readable toolbar 303. As the agent navigates the toolbar, in action 3.2, screen reader module 340 provides audible messages to the agent indicating each control in focus. When the user activates a control of readable toolbar 303 in action 3.3, readable toolbar control module 307 detects the toolbar activity in action 3.4.

Readable toolbar control module 307 may be implemented, for example, as a Java script. Readable toolbar control module 307 invokes a toolbar function of functional control module 309 in action 3.5. Functional control module 309 controls functional toolbar 305 (not visible, as indicated by the dotted line) in the customer service application for users with vision. Functional control module 309 may be implemented, for example, as a Java applet. An example of the interface function of functional control module 309 is given below:

Public String InvokeToolbarFunction (String FunctionName, String Control_ID, String parameter)

This function triggers a function associated with a functional toolbar 305 control. Example invocations of the InvokeToolbarFunction function are provided below:

Tooltip=InvokeToolbarFunction (“GetDynamicTooltip”, “Initiate Phone”, null)

Nothing=InvokeToolbarFunction (“InvokeCommand”, “Initiate Phone”, 26058)

Functional control module 309 uses the parameters provided by readable toolbar control module 307 and, in action 3.7, determines a command to issue in response to activation of the control activated in action 3.3.

As mentioned above, a mapping is provided from each control of readable toolbar 303 to a corresponding control on functional toolbar 305. This mapping to functional toolbar 305 enables user interface 100 to provide equivalent functionality when an HTML control is activated.

For example, a button on functional toolbar 305 may be mapped to a hyperlink with an image. The name of the button can be mapped to the first part of the text name of the hyperlink, and the state of the button can be mapped to the second part of the text name of the hyperlink. For example, a hyperlink may have a name such as “Make Call. Enabled.”

The behavior of a button can also be defined. For example, the equivalent of a mouseover event occurs when a visually disabled user tabs to a control and invokes a hot key, such as H, for help. In response to activating the hot key, the GetDynamicTooltip function of functional toolbar 305 can be called by invoking the following function:

InvokeToolbarFunction (“GetDynamicTooltip”, Control_ID, null).

As a result of this function call, the dynamic tooltip will be updated and presented as text on the readable HTML toolbar in a manner similar to a mouseover event. When a user places focus on that control, screen reader software 340 detects the change and provides an audible message reading the text of the dynamic tooltip.

An edit box of the functional toolbar can be mapped to an edit box of an HTML form control. The text of the edit box can be mapped to the text of the HTML edit box. As the user types in the text, screen reader software can read the information typed as an audible message.

The user can then tab to a button to invoke a command, and the text in the edit box can serve as a parameter for the command. For example, if the user types a telephone extension number in the edit box 208, the user can tab to Initiate Phone Call button 211 to issue a command to make a telephone call to the telephone number entered in edit box 208.

A combo box of the functional toolbar can be mapped to the combo box of HTML form control. The item list of the combo box is mapped to the item list of an HTML combo box. When an item is selected from the combo box, an ItemChanged event calling the InvokeCommand function can be mapped to an ItemChanged event calling the following function:

InvokeToolbarFunction (“InvokeCommand”, Control_ID, selectedItem).

A timer on the functional toolbar can be mapped to a hyperlink. The text of the timer is updated by Functional Control module 309, and in response, screen reader software 340 automatically reads the updated time to provide an audible message.

These mappings from readable toolbar 303 controls to functional toolbar 305 controls may be included, for example, in a data table such as map 320. Map 320 includes a data field indicating the readable toolbar (RT) control 322, a data field indicating the functional toolbar (FT) control 324, and the command 326 associated with the functional toolbar control. One of skill in the art will recognize that the information presented as part of map 320 is a conceptual representation of the types of data that may be referenced. The information may be stored as data fields in memory, in one or more database tables, in one or more files, or in one or more other types of data storage. Furthermore, the information stored can be structured in various alternative ways to associate a command with the readable toolbar (HTML) control.

In action 3.7, functional control module 309 provides the command to web server 330, which passes the command in action 3.8 to communication server 310. The break in the arrow from functional control module 309 to web server 330 for action 3.7 indicates that intermediate software modules and/or hardware devices may be involved in providing the command from functional control module 309 to web server 330. In action 3.9, communication server 310 issues the command via a communication channel to communicate with a media device 350 accessible by the customer. Depending upon the media of the communication, the command may pass through another web server, a middleware server such as an e-mail server, a switching device, or other communication module before reaching the customer's media device 350.

The operation of communication server 310, toolbar 305, and other components of the customer service application described herein are further described in U.S. patent application Ser. No. 09/823,531 (attorney docket M-11528 US, client reference SIEB062/US), filed on Mar. 31, 2001, entitled “User Interface for Multi-Channel Communication” and naming Mingte Chen, Anil K. Annadata, and Kuang Huang as inventors, the application being incorporated herein by reference in its entirety.

FIG. 4 shows another example of the operation of the toolbar of FIG. 2 in receiving an event, such as receiving an incoming customer telephone call. In action 4.1, a customer initiates a customer support request, which corresponds to an event. For example, the customer may place a telephone call or send an e-mail, fax or page to the customer support center. In action 4.2, the event passes from the customer's media device 350 to communication server 310. As noted earlier, the event may pass through intermediate software modules or hardware devices between the customer's media device 350 and communication server 310.

Communication server 310 provides an event response in action 4.3 to web server 330, which in turn provides the event response in action 4.4 to functional control module 309. In action 4.5, functional control module 309 determines the appropriate readable toolbar control to be changed as part of the event response by accessing data stored, for example, as data table map 430. Map 430 includes the mapping between RT control 432, FT control 434, and an event response 436. Again, one of skill in the art will recognize that the information presented as part of map 430 is a conceptual representation only, that the information may be stored as data in one or more other types of temporary or persistent data storage, and that the information may be structured differently.

Upon determining the identity of the readable toolbar control to be changed, in action 4.6, functional control module 309 calls an update readable toolbar function of readable toolbar control module 307. An example interface function is given below:

Function UpdateHTMLControl (Control_ID, argument(s))

This function updates the readable HTML toolbar using arguments, such as the Control_ID of the readable toolbar control and the state of the HTML control. An example invocation of the UpdateHTMLControl function is given below:

UpdateHTMLControl (“Accept Call”, “state: Blinking”)

As noted above, the Control_ID, which corresponds to the name of the control, and the state of the control are combined to provide a name of the hyperlink associated with an image icon. In this example, the name of the hyperlink is “Accept Call. Blinking.”

Readable toolbar control module 307 uses provides this hyperlink name to the readable toolbar in action 4.7 to update the name of the corresponding HTML control. Assigning new values for the name of the control and its status are changes in the readable toolbar control, and these changes are automatically detected by screen reader module 340. The response to this function call is to read an audible message containing the name of the hyperlink, “Accept Call. Blinking,” in action 4.8, which indicates an incoming telephone call.

System Suitable for Implementing the Present Invention

FIG. 5 depicts a block diagram of a computer system 10 suitable for implementing the present invention. Computer system 10 includes a bus 12 which interconnects major subsystems of computer system 10 such as a central processor 14, a system memory 16 (typically RAM, but which may also include ROM, flash RAM, or the like), an input/output controller 18, an external audio device such as a speaker system 20 via an audio output interface 22, an external device such as a display screen 24 via display adapter 26, serial ports 28 and 30, a keyboard 32 (interfaced with a keyboard controller 33), a storage interface 34, a floppy disk drive 36 operative to receive a floppy disk 38, and a CD-ROM drive 40 operative to receive a CD-ROM 42. Also included are a mouse 46 (or other point-and-click device, coupled to bus 12 via serial port 28), a modem 47 (coupled to bus 12 via serial port 30) and a network interface 48 (coupled directly to bus 12).

Bus 12 allows data communication between central processor 14 and system memory 16, which may include both read only memory (ROM) or flash memory (neither shown), and random access memory (RAM) (not shown), as previously noted. The RAM is generally the main memory into which the operating system and application programs are loaded and typically affords at least 16 megabytes of memory space. The ROM or flash memory may contain, among other code, the Basic Input-Output system (BIOS) which controls basic hardware operation such as the interaction with peripheral components. Applications resident with computer system 10 are generally stored on and accessed via a computer readable medium, such as a hard disk drive (e.g., fixed disk 44), an optical drive (e.g., CD-ROM drive 40), floppy disk unit 36 or other storage medium. Additionally, applications may be in the form of electronic signals modulated in accordance with the application and data communication technology when accessed via network modem 47 or interface 48.

Storage interface 34, as with the other storage interfaces of computer system 10, may connect to a standard computer readable medium for storage and/or retrieval of information, such as a fixed disk drive 44. Fixed disk drive 44 may be a part of computer system 10 or may be separate and accessed through other interface systems. Many other devices can be connected such as a mouse 46 connected to bus 12 via serial port 28, a modem 47 connected to bus 12 via serial port 30 and a network interface 48 connected directly to bus 12. Modem 47 may provide a direct connection to a remote server via a telephone link or to the Internet via an internet service provider (ISP). Network interface 48 may provide a direct connection to a remote server via a direct network link to the Internet via a POP (point of presence). Network interface 48 may provide such connection using wireless techniques, including digital cellular telephone connection, Cellular Digital Packet Data (CDPD) connection, digital satellite data connection or the like.

Many other devices or subsystems (not shown) may be connected in a similar manner (e.g., bar code readers, document scanners, digital cameras and so on). Conversely, it is not necessary for all of the devices shown in FIG. 5 to be present to practice the present invention. The devices and subsystems may be interconnected in different ways from that shown in FIG. 5. The operation of a computer system such as that shown in FIG. 5 is readily known in the art and is not discussed in detail in this application. Code to implement the present invention may be stored in computer-readable storage media such as one or more of system memory 16, fixed disk 44, CD-ROM 42, or floppy disk 38. Additionally, computer system 10 may be any kind of computing device, and so includes personal data assistants (PDAs), network appliances, X-window terminals or other such computing devices. The operating system provided on computer system 10 may be MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, Linux® or other known operating system. Computer system 10 also supports a number of Internet access tools, including, for example, an HTTP-compliant web browser having a JavaScript interpreter, such as Netscape Navigator 3.0, Microsoft Explorer® 3.0 and the like.

Moreover, regarding the messages and/or data signals described herein, those skilled in the art will recognize that a signal may be directly transmitted from a first block to a second block, or a signal may be modified (e.g., amplified, attenuated, delayed, latched, buffered, inverted, filtered or otherwise modified) between the blocks. Although the signals of the above described embodiment are characterized as transmitted from one block to the next, other embodiments of the present invention may include modified signals in place of such directly transmitted signals as long as the informational and/or functional aspect of the signal is transmitted between blocks. To some extent, a signal input at a second block may be conceptualized as a second signal derived from a first signal output from a first block due to physical limitations of the circuitry involved (e.g., there will inevitably be some attenuation and delay). Therefore, as used herein, a second signal derived from a first signal includes the first signal or any modifications to the first signal, whether due to circuit limitations or due to passage through other circuit elements which do not change the informational and/or final functional aspect of the first signal.

Other Embodiments

The present invention is well adapted to attain the advantages mentioned as well as others inherent therein. While the present invention has been depicted, described, and is defined by reference to particular embodiments of the invention, such references do not imply a limitation on the invention, and no such limitation is to be inferred. The invention is capable of considerable modification, alteration, and equivalents in form and function, as will occur to those ordinarily skilled in the pertinent arts. The depicted and described embodiments are examples only, and are not exhaustive of the scope of the invention.

The foregoing described embodiments include components contained within other components. It is to be understood that such architectures are merely examples, and that in fact many other architectures can be implemented which achieve the same functionality. In an abstract but still definite sense, any arrangement of components to achieve the same functionality is effectively “associated” such that the desired functionality is achieved. Hence, any two components herein combined to achieve a particular functionality can be seen as “associated with” each other such that the desired functionality is achieved, irrespective of architectures or intermediate components. Likewise, any two components so associated can also be viewed as being “operably connected,” or “operably coupled,” to each other to achieve the desired functionality.

The foregoing detailed description has set forth various embodiments of the present invention via the use of block diagrams, flowcharts, and examples. It will be understood by those within the art that each block diagram component, flowchart step, operation and/or component illustrated by the use of examples can be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, or any combination thereof.

The present invention has been described in the context of fully functional computer systems; however, those skilled in the art will appreciate that the present invention is capable of being distributed as a program product in a variety of forms, and that the present invention applies equally regardless of the particular type of signal bearing media used to actually carry out the distribution. Examples of signal bearing media include recordable media such as floppy disks and CD-ROM, transmission type media such as digital and analog communications links, as well as media storage and distribution systems developed in the future.

The above-discussed embodiments may be implemented by software modules that perform certain tasks. The software modules discussed herein may include script, batch, or other executable files. The software modules may be stored on a machine-readable or computer-readable storage medium such as a disk drive. Storage devices used for storing software modules in accordance with an embodiment of the invention may be magnetic floppy disks, hard disks, or optical discs such as CD-ROMs or CD-Rs, for example. A storage device used for storing firmware or hardware modules in accordance with an embodiment of the invention may also include a semiconductor-based memory, which may be permanently, removably or remotely coupled to a microprocessor/memory system. Thus, the modules may be stored within a computer system memory to configure the computer system to perform the functions of the module. Other new and various types of computer-readable storage media may be used to store the modules discussed herein.

The above description is intended to be illustrative of the invention and should not be taken to be limiting. Other embodiments within the scope of the present invention are possible. Those skilled in the art will readily implement the steps necessary to provide the structures and the methods disclosed herein, and will understand that the process parameters and sequence of steps are given by way of example only and can be varied to achieve the desired structure as well as modifications that are within the scope of the invention. Variations and modifications of the embodiments disclosed herein can be made based on the description set forth herein, without departing from the scope of the invention.

Consequently, the invention is intended to be limited only by the scope of the appended claims, giving full cognizance to equivalents in all respects. 

1. A method comprising: determining that a readable control of a user interface is activated; identifying a command associated with activation of the readable control, wherein the identifying the command comprises using a mapping between the readable control and a functional control, the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function; and causing the functional control to issue the command in response to the activation of the readable control.
 2. (canceled)
 3. (canceled)
 4. The method of claim 1 further comprising: determining that a second readable control has obtained focus; and providing text for an audible message associated with the second readable control.
 5. The method of claim 4 further comprising: providing text for a second audible message in response to receiving a hot key activation, wherein the hot key is associated with the second readable control.
 6. The method of claim 1 further comprising: providing text for an audible message associated with the readable control.
 7. The method of claim 1 further comprising: providing text for an audible message in response to a change of state of the readable control.
 8. The method of claim 1 wherein the readable control is activated using a hot key.
 9. The method of claim 1 further comprising: causing a state of the readable control to change in response to obtaining an event.
 10. A method comprising: causing a state of a readable control of a user interface to change in response to obtaining an incoming communication event; and identifying a functional control that corresponds to the readable control, wherein the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function.
 11. The method of claim 10 further comprising: providing text for an audible message in response to the change in the state.
 12. A user interface module comprising: determining instructions to determine that a readable control of a user interface presented by the user interface module is activated; identifying instructions to identify a command associated with activation of the readable control, wherein the identifying instructions comprise using instructions to use a mapping between the readable control and a functional control, the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function; and issuing instructions to issue the command in response to the activation of the readable control.
 13. (canceled)
 14. (canceled)
 15. The user interface module of claim 12 further comprising: second determining instructions to determine that a second readable control of the user interface has obtained focus; and providing instructions to provide text for an audible message associated with the second readable control.
 16. The user interface module of claim 12 further comprising: providing instructions to provide text for an audible message associated with the readable control.
 17. A user interface module comprising: causing instructions to cause a state of a readable control of a user interface presented by the user interface module to change in response to obtaining an incoming communication event; and identifying instructions to identify a functional control that corresponds to the readable control, wherein the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function.
 18. The user interface module of claim 17 further comprising: providing instructions to provide text for an audible message in response to the change in the state.
 19. A system comprising: determining means for determining that a readable control of a user interface is activated; and identifying means for identifying a command associated with activation of the readable control, wherein the identifying means comprise using means for using a mapping between the readable control and a functional controls the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function; and issuing means for issuing the command in response to the activation of the readable control.
 20. (canceled)
 21. (canceled)
 22. The system of claim 19 further comprising: second determining means for determining that a second readable control has obtained focus; and providing means for providing text for an audible message associated with the second readable control.
 23. The system of claim 19 further comprising: providing means for providing text for an audible message associated with the readable control.
 24. A system comprising: causing means for causing a state of a readable control of a user interface to change in response to obtaining an incoming communication event; and identifying means for identifying a functional control that corresponds to the readable control, wherein the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function.
 25. The system of claim 24 further comprising: providing means for providing text for an audible message in response to the change in the state.
 26. A computer program product comprising: determining instructions to determine that a readable control of a user interface is activated; identifying instructions to identify a command associated with activation of the readable control, wherein the identifying instructions comprise using instructions to use a mapping between the readable control and a functional control, the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function; issuing instructions to cause the functional control to issue the command in response to the activation of the readable control; and a computer-readable medium to store the determining instructions, the using instructions, the identifying instructions, and the issuing instructions.
 27. (canceled)
 28. (canceled)
 29. The computer program product of claim 26 further comprising: second determining instructions to determine that a second readable control has obtained focus; and providing instructions to provide text for an audible message associated with the second readable control; wherein the computer-readable medium further stores the second determining instructions and the providing instructions.
 30. The computer program product of claim 26 further comprising: providing instructions to provide text for an audible message associated with the readable control; wherein the computer-readable medium further stores the providing instructions.
 31. A computer program product comprising: causing instructions to cause a state of a readable control of a user interface to change in response to obtaining an incoming communication event; and identifying instructions to identify a functional control that corresponds to the readable control, wherein the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function; and a computer-readable medium to store the causing instructions and the identifying instructions.
 32. The computer program product of claim 31 further comprising: providing instructions to provide text for an audible message in response to the change in the state; wherein the computer-readable medium further stores the providing instructions.
 33. A computer system comprising: a processor for executing computer instructions; and a memory comprising the computer instructions, wherein the computer instructions comprise: determining instructions to determine that a readable control of a user interface is activated; and identifying instructions to identify a command associated with activation of the readable control, wherein the identifying instructions comprise using instructions to use a mapping between the readable control and a functional control, the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function; and issuing instructions to cause the functional control to issue the command in response to the activation of the readable control.
 34. (canceled)
 35. (canceled)
 36. The computer system of claim 33 wherein the computer instructions further comprise: second determining instructions to determine that a second readable control has obtained focus; and providing instructions to provide text for an audible message associated with the second readable control.
 37. The computer system of claim 33 wherein the computer instructions further comprise: providing instructions to provide text for an audible message associated with the readable control.
 38. A computer system comprising: a processor for executing computer instructions; a memory comprising the computer instructions, wherein the computer instructions comprise: causing instructions to cause a state of a readable control of a user interface to change in response to obtaining an incoming communication event; and identifying instructions to identify a functional control that corresponds to the readable control, wherein the functional control is configured to provide a function, and the readable control is a non-functional control by virtue of being incapable of providing the function.
 39. The computer system of claim 38 wherein the computer instructions further comprise: providing instructions to provide text for an audible message in response to the change in the state. 